Subject: Summary minutes of HPR SIG meeting at AIW 6, 13 Oct 94

From: "Marcia Peters (8-444-4380)" <[email-masked]>
Date: Mon, 31 Oct 94 10:24:18 EST

o PROCEDURE.  Is the HPR spec at the right level of completeness to be
  eligible for AP?  Yes, people have been able to code from it.

o NETWORK MANAGEMENT.  SNMP management for HPR is a new work area for
  the SIG.  Leo Temoshenko gave an overview of an HPR MIB and APPN MIB
  extensions developed by IBM.

o APPN/HPR TRANSPORT.  A detailed document review ensued, led by Ray
  Bird and Lap Huynh.  Their answers to questions are posted in a
  separate note.

  From your write-in comments, I know that several of you became
  impatient with the long discussion of path switch timers.  I allowed
  this discussion to continue because the issue was not simply a default
  timers, but a potentially serious protocol deadlock/hang condition.
  Architectural design meetings often require detailed examination of
  issues in order to flush out protocol bugs, and this was a case where
  the discussion was necessary and worthwhile.

  Many issues were resolved and questions answered.  (See detailed notes
  by Ray Bird and Lap Huynh, posted separately.)

AP APPROVAL

The SIG and later the AIW plenary granted AP approval, with the
following items still requiring resolution:

  - NETWORK MANAGEMENT

    . HPR MIB

      After discussion, consensus was to make the HPR MIB a separate
      document on its own approval schedule.  If the HPR spec is CP
      before the MIB, it will not hold up coding.  The MIB depends on
      the APPC/APPN MIBs, which are not yet CP either.  It was suggested
      to combine the HPR MIB work with the APPN MIB work, get AIW
      approval, then submit to IETF to be anchored at a standard
      codepoint.

    . SNMP OVER SNA.

      HPR management has a dependency on a standard for SNMP/SNA, which
      does not yet exist.  I said I believed IBM plans to make a
      proposal on this on or before the next AIW.

    . ALERTS.

      Detailed alert information needs to be added to the HPR spec.  The
      events that trigger an alert are already documented.  Members are
      encouraged to submit any additional alerts.  Still needed are the
      alert codepoints, problem description, and corrective action (see
      SNA/MS Reference).  IBM was asked to provide a schedule for the
      latter items, which are needed for CP.  This info is needed ASAP
      by the people working on the APPN/HPR MIB for mapping into SNMP
      traps.

  - Many thought the Class of Service proposal in the AWP was
    unacceptable, in that it could result in loss of function for
    customers.  This proposal needs to be reworked.  Suggestions made by
    Dave Bryant (3Com) and Matthew Finlayson (DCL), which were generally
    received positively by the SIG, could form the basis of a revised
    proposal.

  - The liveness timer default value needs further study.  In
    particular, if IBM has a particular reason for wanting the timer to
    be 30 minutes, they need to come forward with an explanation.
    Otherwise a much shorter value should be chosen.

  - The XID ERP settings for X.25 links need to be specified.

  - Some minor editorial changes are neeeded.

  - Need to specify APPN option set dependencies.

  - A request was made that the HPR spec specify Layer 2 and Layer 3
    settings for HPR/ATM.  (I suspect the new ATM BOF will prove to the
    the appropriate forum for this work.)

Thanks, everybody, for your participation.

Marcia Peters, HPR SIG Chair